home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19990725-20000114
/
000241_news@columbia.edu _Wed Oct 27 16:28:09 1999.msg
< prev
next >
Wrap
Internet Message Format
|
2000-01-13
|
2KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id QAA26701
for <kermit.misc@watsun.cc.columbia.edu>; Wed, 27 Oct 1999 16:28:08 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id QAA18020
for kermit.misc@watsun.cc.columbia.edu; Wed, 27 Oct 1999 16:04:19 -0400 (EDT)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: Clarence Dold <dold@yellow.rahul.net>
Subject: Re: Input timings
Date: 27 Oct 1999 19:41:08 GMT
Organization: a2i network
Message-ID: <7v7kgk$3cb$1@samba.rahul.net>
To: kermit.misc@columbia.edu
Michael Hamelin <hamelin@ici.net> wrote:
: a prompt. I have given the input command a wait of 600. This is to wait for
: 10 minutes, worse case.. I have tried this
: in my script and the thing waits 20 seconds and then goes to the next item
Let's get simpler.
I built a script "wait":
run date
input 600 f
run date
Kermit
take wait
I can type lots of characters... If I avoid hitting an "f", I get two
time stamps, 10 minutes apart.
I haven't connected to anything. If this works, then you might want to
connect to the other system, and run the take script again. If it times
out while attached to some other system, then you need to do a log session,
to see what characters are causing your input to trip.
I had a system that was displaying the time, updated every few seconds,
which messed up my session logs for my purposes. Perhaps something like
that is triggering the wait-for-prompt in your case.
--
---
Clarence A Dold - dold@network.rahul.net
- Pope Valley & Napa CA.